-
Notifications
You must be signed in to change notification settings - Fork 310
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Overriding desired MAC parameters and defaults #101
Conversation
e0d2239
to
20c8b26
Compare
9beba6b
to
3f466da
Compare
Looks like our config package does not support custom types:
I will address this next week |
It does support some, indeed |
348ac03
to
653fd18
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No specific changes requested, just a couple of comments related to API and config.
|
@johanstokking @htdvisser any update on this? |
You didn't request my review, so I only commented on the API things that I noticed. I'll remove my review request. If you do want a full review from me, please re-request. |
2a32648
to
c5d3ae3
Compare
@htdvisser I made a bunch more changes from #144 here, since I was modifying |
ed9b41f
to
4974518
Compare
Summary:
References #5
Closes #60
Closes #104
Closes #105
Closes #144
Closes #159
Changes:
DeviceProfile
as well as additional MAC parameters toMACSettings
DeviceProfile
from Backend InterfacesMACSettings
optionalMACSettings
to fallback to if not defined by the deviceRxDelay
to5s
by defaultsession
for OTAA devices(Set OTAA devices and specify DevAddr, AppSKey, NwkSKey, FCntUp, FCntDown #104)DefaultMACParameters
Notes for Reviewers:
Other MAC parameters, if required, will be added in another PR - please create an issue
I tested this with a Class C device in a simulator
Release notes:
Backwards-incompatible API and DB-model changes were introduced. Any created devices need to be recreated.